Change repository link to claude-memory-extractor - #2
Conversation
Updated repository links for local installation instructions.
WalkthroughDocumentation update that changes repository clone URLs from claude-memory to claude-memory-extractor and adds npm build and link steps to both global installation and local development instructions. No functional code changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
README.md(1 hunks)
🔇 Additional comments (1)
README.md (1)
67-73: Verify consistency with Option 1 installation approach.Option 2 correctly omits
npm linksince it runs the CLI directly from the built distribution, which is appropriate for local development. Confirm this distinction is intentional and that users running the direct command (./dist/cli.js extract) will work as expected without global installation.
| git clone https://github.com/obra/claude-memory-extractor.git | ||
| cd claude-memory-extractor | ||
| npm install && npm run build | ||
| npm link | ||
| ``` |
There was a problem hiding this comment.
🧩 Analysis chain
Verify the repository URL is correct and reachable.
The clone URL has been updated from claude-memory to claude-memory-extractor. Confirm that this repository exists, is accessible, and reflects the current source of truth for this project.
🏁 Script executed:
#!/bin/bash
# Verify the new repository URL is accessible and contains the expected code
git ls-remote https://github.com/obra/claude-memory-extractor.git HEAD > /dev/null 2>&1
if [ $? -eq 0 ]; then
echo "✓ Repository is accessible"
git ls-remote https://github.com/obra/claude-memory-extractor.git | head -5
else
echo "✗ Repository URL is not reachable"
fiLength of output: 246
Repository URL verification passed. Now checking for any other references to the old repository name in the codebase.
---
🏁 Script executed:
```shell
#!/bin/bash
# Search for remaining references to "claude-memory" (without -extractor suffix)
# in the codebase to ensure consistency
rg -n "claude-memory(?!-extractor)" --type md --type json --type yaml --type txt --type js --type ts 2>/dev/null || echo "No matches or search completed"
Length of output: 30
🏁 Script executed:
#!/bin/bash
# Also check for any repository references that might be in package.json or similar config files
fd -e "package.json" -e "package-lock.json" -e ".github" -type f | head -20Length of output: 170
🏁 Script executed:
#!/bin/bash
# Get a count of all "claude-memory" occurrences to understand scope
rg -c "claude-memory" 2>/dev/null | grep -v ":0$" || echo "Search completed"Length of output: 69
Found lingering references to "claude-memory" across multiple files. Examining the actual content to determine if these are incomplete updates or intentional references.
---
🏁 Script executed:
```shell
#!/bin/bash
# Show context for "claude-memory" references in README.md
rg -n -B2 -A2 "claude-memory" README.md
Length of output: 1014
🏁 Script executed:
#!/bin/bash
# Check src/cli.ts references
rg -n -B2 -A2 "claude-memory" src/cli.tsLength of output: 533
🏁 Script executed:
#!/bin/bash
# Check package.json
rg -n "claude-memory" package.jsonLength of output: 123
🏁 Script executed:
#!/bin/bash
# Check docs/guides/quick-start.md
rg -n -B2 -A2 "claude-memory" docs/guides/quick-start.mdLength of output: 535
Update inconsistencies: repository name changes not applied uniformly across the codebase.
The README.md lines 58-62 are correctly updated to use the new claude-memory-extractor repository URL. However, the broader repository rename is incomplete:
package.jsonline 31: Repository URL still referenceshttps://github.com/obra/claude-memory.gitpackage.jsonline 2: Package name still"claude-memory"(should align with repository name)src/cli.tsline 74: Help text URL still points tohttps://github.com/obra/claude-memorydocs/guides/quick-start.mdlines 18-19: Clone instructions still reference old repository and directory name
These should be updated to maintain consistency with the new repository name across all user-facing and configuration references.
🤖 Prompt for AI Agents
In README.md lines 58-62 and across the repo (package.json lines 31 and 2,
src/cli.ts line 74, docs/guides/quick-start.md lines 18-19) the project was
partially renamed to claude-memory-extractor but several user-facing and config
references remain as claude-memory or the old GitHub URL; update package.json
name (line 2) to "claude-memory-extractor", update the repository URL (line 31)
to https://github.com/obra/claude-memory-extractor.git, change the help text URL
in src/cli.ts (line 74) to the new repo URL, and update the clone/path
instructions in docs/guides/quick-start.md (lines 18-19) to use the new
repository and directory name so all references are consistent.
Updated repository links for local installation instructions.
Motivation and Context
How Has This Been Tested?
Breaking Changes
Types of changes
Checklist
Additional context
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.